Azure Maps Elevation API (preview:1.0)

2025/08/14 • 5 deleted methods

Elevation_GetDataForPoints (removed)
Description **Applies to**: S1 pricing tier. The Get Data for Points API provides elevation data for one or more points. A point is defined in lat,long coordinate format. Due to the URL character length limit of 2048, it's not possible to pass more than 100 coordinates as a pipeline delimited string in a URL GET request. If you intend to pass more than 100 coordinates as a pipeline delimited string, use the [POST Data For Points](https://docs.microsoft.com/en-us/rest/api/maps/elevation/postdataforpoints).
Reference Link ¶

⚼ Request

GET:  /elevation/point/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
points: array ,
}

⚐ Response (200)

{
data:
[
{
coordinate:
{
latitude: number ,
longitude: number ,
}
,
elevationInMeter: number ,
}
,
]
,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
Elevation_PostDataForPoints (removed)
Description **Applies to**: S1 pricing tier. The Post Data for Points API provides elevation data for multiple points. A point is defined in lat/lon coordinate format. Use the POST endpoint only if you intend to pass multiple points in the request. If you intend to pass a single coordinate into the API, use the [GET Data For Points API](https://docs.microsoft.com/en-us/rest/api/maps/elevation/getdataforpoints).
Reference Link ¶

⚼ Request

POST:  /elevation/point/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
pointsRequestBody:
{
lat: number ,
lon: number ,
}
,
}

⚐ Response (200)

{
data:
[
{
coordinate:
{
latitude: number ,
longitude: number ,
}
,
elevationInMeter: number ,
}
,
]
,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
Elevation_GetDataForPolyline (removed)
Description **Applies to**: S1 pricing tier. The Get Data for Polyline API provides elevation data along a polyline. A polyline is defined by passing in between 2 and N endpoint coordinates separated by a pipe ('|') character. In addition to passing in endpoints, customers can specify the number of sample points that will be used to divide polyline into equally spaced segments. Elevation data at both start and endpoints and equally spaced points along the polyline will be returned. A line between two endpoints is a straight Cartesian line, the shortest line between those two points in the coordinate reference system. Note that the point is chosen based on Euclidean distance and may markedly differ from the geodesic path along the curved surface of the reference ellipsoid.
Reference Link ¶

⚼ Request

GET:  /elevation/line/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
lines: array ,
samples: number ,
}

⚐ Response (200)

{
data:
[
{
coordinate:
{
latitude: number ,
longitude: number ,
}
,
elevationInMeter: number ,
}
,
]
,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
Elevation_PostDataForPolyline (removed)
Description **Applies to**: S1 pricing tier. The Post Data for Polyline API provides elevation data along a polyline. A polyline is defined by passing in between 2 and N endpoint coordinates separated by a pipe ('|') character. In addition to passing in endpoints, customers can specify the number of sample points that will be used to divide polyline into equally spaced segments. Elevation data at both start and end points and equally spaced points along the polyline will be returned. A line between two endpoints is a straight Cartesian line, the shortest line between those two points in the coordinate reference system. Note that the point is chosen based on Euclidean distance and may markedly differ from the geodesic path along the curved surface of the reference ellipsoid.
Reference Link ¶

⚼ Request

POST:  /elevation/line/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
linesRequestBody:
{
lat: number ,
lon: number ,
}
,
samples: number ,
}

⚐ Response (200)

{
data:
[
{
coordinate:
{
latitude: number ,
longitude: number ,
}
,
elevationInMeter: number ,
}
,
]
,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
Elevation_GetDataForBoundingBox (removed)
Description **Applies to**: S1 pricing tier. The Get Data for Bounding Box API provides elevation data at equally spaced locations within a bounding box. A bounding box is defined by the coordinates for two corners (southwest, northeast) and then subsequently divided into rows and columns. Elevations are returned for the vertices of the grid created by the rows and columns. Up to 2,000 elevations can be returned in a single request. The returned elevation values are ordered, starting at the southwest corner, and then proceeding west to east along the row. At the end of the row, it moves north to the next row, and repeats the process until it reaches the far northeast corner.
Reference Link ¶

⚼ Request

GET:  /elevation/lattice/{format}
{
x-ms-client-id: string ,
subscription-key: string ,
api-version: string ,
format: string ,
bounds: array ,
rows: number ,
columns: number ,
}

⚐ Response (200)

{
data:
[
{
coordinate:
{
latitude: number ,
longitude: number ,
}
,
elevationInMeter: number ,
}
,
]
,
}

⚐ Response (400)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (401)

{
$headers:
{
www-authenticate: string ,
}
,
$schema:
{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}
,
}

⚐ Response (403)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (404)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}

⚐ Response (500)

{
error:
{
code: string ,
message: string ,
details:
[
string ,
]
,
target: string ,
}
,
}